You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
renovateBot
changed the title
chore(deps): update oss/v2/kubernetes/apiserver-network-proxy/agent docker tag to v0.32.1-3
chore(deps): update oss/v2/kubernetes/apiserver-network-proxy/agent docker tag to v0.32.1-4
Apr 9, 2026
renovateBot
changed the title
chore(deps): update oss/v2/kubernetes/apiserver-network-proxy/agent docker tag to v0.32.1-4
chore(deps): update oss/v2/kubernetes/apiserver-network-proxy/agent docker tag to v0.32.1-5
Apr 20, 2026
renovateBot
changed the title
chore(deps): update oss/v2/kubernetes/apiserver-network-proxy/agent docker tag to v0.32.1-5
chore(deps): update oss/v2/kubernetes/apiserver-network-proxy/agent docker tag to v0.32.1-6
Jun 3, 2026
renovateBot
changed the title
chore(deps): update oss/v2/kubernetes/apiserver-network-proxy/agent docker tag to v0.32.1-6
chore(deps): update oss/v2/kubernetes/apiserver-network-proxy/agent docker tag to v0.32.1-7
Jun 12, 2026
🕵️ AgentBaker Linux Gate Detective — Build 167836139 (Run AgentBaker E2E) FAILED — known shared-cluster infra outage, not caused by this PR.
TL;DR
Matches existing wiki signature kubenet-v5-node-not-ready-scriptless on shared westus3 cluster abe2e-kubenet-v5-150ee. Repair item #38403603 already tracking this fleet/apiserver issue. This PR is a Renovate Docker tag bump for oss/v2/kubernetes/apiserver-network-proxy/agent → v0.32.1-7, which does not touch kubelet, CSE, NBC, or any node provisioning path.
3-level RCA
1. Surface symptom — Every failed scenario terminates at: kube.go:195 🔴 FAIL: "<vmss>" haven't appeared in k8s API server: context deadline exceeded after ~738s, on cluster abe2e-kubenet-v5-150ee (rg abe2e-westus3).
2. Corroboration — Same back-to-back run on main (build 167835297, no PR) reproduces the identical signature on the same shared cluster, with the same abe2e-kubenet-v5-150ee target — independent corroboration that this is shared-cluster apiserver throttling, not anything specific to PR #7906's commit 00d1e47d. Pattern reproduced on 7 unrelated PRs in the last 24h (#8104, #8294, #8509, #8659, #8667, #8694, #8698) plus consecutive TME pipeline (def 451455) builds on a different westus cluster (abe2e-kubenet-v5-e7055).
3. Root-cause challenge — Strongest alternative: PR-caused regression via the new apiserver-network-proxy/agent image. Why less likely: the proxy-agent is a control-plane-side image (HCP), not consumed by the VHD or node CSE; bumping its docker tag in parts/common/components.json cannot affect kubelet's ability to register on the data-plane VMSS. Failure point is pre-kubelet-registration, before any apiserver-network-proxy interaction would matter. Symptom is identical to the main-branch run at the same time on the same cluster — strong infra signal.
Classification
Test infrastructure / shared-cluster fleet stress (not PR-caused)
Wiki signature: kubenet-v5-node-not-ready-scriptless (Count → 14 distinct builds incl. this one and the parallel main run)
Confidence: High that this is the known infra outage; High that the PR is unrelated.
Recommended next action
For this PR: safe to rebase/rerun once shared clusters recover; no code change required.
Owner of the underlying issue: AgentBaker E2E test-infra (repair item #38403603).
renovateBot
changed the title
chore(deps): update oss/v2/kubernetes/apiserver-network-proxy/agent docker tag to v0.32.1-7
chore(deps): update oss/v2/kubernetes/apiserver-network-proxy/agent docker tag to v0.32.1-8
Jun 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
componentsThis pull request updates cached components on Linux or Windows VHDsrenovateThis pull request was created by renovate
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v0.32.1-2→v0.32.1-8Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.